gardening #1164
Closed
gardening #1164
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
marxian
commented
Sep 6, 2021
marxian
commented
- feat: begin migration
- feat: typescript
- feat: typescript
- feat: typescript
- feat: typescript
- feat: typescript
- feat: typescript
- feat: typescript
- feat: typescript
- feat: typescript
- fix: types for emotion
- fix: start upgrade to emotion 11
- fix: emotion css prop
- feat: do some auth typing
- chore: typing
- feat: IT RENDERS
- wip
- chore: codemode anon
- feat: render images better
- feat: render loo map without markers
- fix: edit loo page
- feat: onwards
- feat: graphql webpack loader
- fix: typefest
- feat: switch to esbuild
- u turn on esbuild for now
- add next config for proxying api reqs
- fix routing for shallow loading of individual loo pages
- edit page working I think maybe perhaps
- remove page
- get the other pages to route correctly, still a few more to fix
- install gql apollo codegen
- codegen on graphql
- disable gql wp loader, break ALL the things
- ship nearby loos query out to its own file for codegen
- prove out new codegen is working for loos by proximity on the index page.
- get gen client hook to work properly
- tidyup
- improve codegen command so it spins up api for code generation to work
- fix dynamic loading of toilets so that they load successfully on initial page render
- fix info panels for individual toilets
- messing around getting the build to pass, skipping type checking and eslint for now, but it passes.. hooray!!
- no idea how this workflow works haha
- undo
- put names back for package json
- change build out dir
- remove index from public
- put build output back
- messing with build dir
- put back, wait on vercel config check
- sketch a plan
- api gardening (api gardening #1147)
- fix chicken and egg problem with codegen for nextjs client depending on the project running correctly.. the project depends on the generated files!
- fix so we use one typedef file for both api impls
- feat: auth with nextjs-auth0 (feat: auth with nextjs-auth0 #1150)
- chore: update codegen tools et al
- fix: update to latest apollo and graphql
- chore: fix lint-staged
…eslint for now, but it passes.. hooray!!
* refactor: ramshackle move of api to next.js proper * refactor: minor updeps and config cleaning
…on the project running correctly.. the project depends on the generated files!
Install some handlers, protect some pages, wire up the header logout button Also a lot of pretty brutal cleanup. Sorry for the mixed commit. Carried away.
|
This pull request is being automatically deployed with Vercel (learn more). gbptm – ./🔍 Inspect: https://vercel.com/neontribe/gbptm/B3eYPU4D3gjxxJogLGnzqCMhQn9X gbptm-next – ./🔍 Inspect: https://vercel.com/neontribe/gbptm-next/GGUR2oEAoVooDUdu3uVCDmdHBnFF |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.