I'm looking into the code about the FemPosDeviationSmoother (one strategy of the DiscretePointsReferenceLineSmoother), but find it difficult to understand. Is there any paper or document for reference? Thanks a lot.

2.1 emphasizes the use of their new Component based methodology, with things like the <Query> and <Mutation> component. They've pushed for it to the point that it is quickly becoming difficult to find documentation for the 2.0 methods used in learnapollo.

A full update to 2.1 for apollo sections seems to be in order.

It would be great to have this project as video series or as step by step tutorial where you learn bit by bit and have a functional product in the end.

The api server and webpack dev server should be restarted when the redwood.toml configuration is modified.

Related: #478

It would be really cool to have a section below in the readme to showcase projects built with RAN, or at least maybe somewhere where people can add links to their projects that they've built with this framework! (SUGGESTION)

Add native Expo Google API integration for login as a module next to WebBrowser implementation, e.g. auth/expo-google next to auth/google
Relevant docs:
https://docs.expo.io/versions/v31.0.0/sdk/google

All @Urigo projects have proper documentation. We should possibly create simple website and start documenting things there. This is crutial to move from beta phase. I can create source code but we need domain as well

apollo-link-ws comes with the 'graphql-ws' Sec-Websocket-Protocol header.
I would like to change tha

The link is broken in the readme file in the following text. Please share the link or update it on the readme file.

You can more learn about the idea behind GraphQL boilerplates here.

https://easy-peasy.now.sh/docs/introduction/

Easy Peasy provides you with an intuitive API to quickly and easily manage the state for your React application. Batteries are included - no configuration is required to support derived state, API calls, performance optimisation, developer tools etc.

When using a local client cache, it's helpful to have a default state that only gets initialized the first time the cache is created, and not when the cache is restored from persist storage.

With 3.0, this doesn't seem simple anymore.

#85 has an old example of setting up defaults:

Little type in following section of README.md file:

Server-side rendering vue
Very easy way to render your fonrtend on the server automatically when a user first loads the app.

Issue: 'fonrtend' should be spelled as 'frontend'

SyntaxError: Error while loading rule 'graphql/template-strings': Unexpected token  in JSON at position 0
Occurred while linting /Users/devalias/dev/REDACTED/schema.graphql
    at JSON.parse (<anonymous>)
    at Object.readSchema (/Users/devalias/dev/REDACTED/node_modules/graphql-config/lib/utils.js:141:38)
    at GraphQLProjectConfig.getSchema (/Users/devalias/dev/REDACTED/node_modules/g

As a new user of your plugin it was not obvious to understand how to provide custom variables. After some time I noticed "Toggle variable editor" but after that I was confused in which format I should provide my variable: JSON, YML or another.

Describe the solution you'd like
Tutorial with step by step would help very much.

Developing on the default config with localhost:3000 is fine.

However when I tried to test the local dev version from a device in the local network, say 192.169.110.1:3000, one of the client requests is still pointing to localhost:3000. Specifically, it's http://localhost:3000/__meteor__/dynamic-import/fetch, which makes the app unresponsive/unable to login from devices other than localhost.