Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use TypeScript #601

Open
jkomoros opened this issue May 27, 2022 · 5 comments
Open

Use TypeScript #601

jkomoros opened this issue May 27, 2022 · 5 comments
Labels
cleanup No change in user behavior, just code cleanup and refactoring

Comments

@jkomoros
Copy link
Owner

No description provided.

@jkomoros jkomoros added the cleanup No change in user behavior, just code cleanup and refactoring label May 27, 2022
@jkomoros
Copy link
Owner Author

jkomoros commented May 29, 2022

@jkomoros
Copy link
Owner Author

jkomoros commented May 29, 2022

@jkomoros
Copy link
Owner Author

jkomoros commented May 29, 2022

Move all js to ts (including config.secret.json generation), have a git_ignore of src/**.js,

Re copy config.SECRET.json .

Don't have tsc inline files in src (that's super-confusing/messy), just have it in build_ts/

Make sure npm run build works (even if you haven't done npm run serve)

Get eslint errors suprressed in generated files in src/

jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
This requires re-runing `gulp inject-config` (or just mv'ing the file).

Having it be inside the src directory makes it less confusing/weird for other tools.

Part of #601.
jkomoros added a commit that referenced this issue May 30, 2022
Lots and lots of emitted warnings from typescript, but dev server works, things build.

Typescript emits its output into src/ alongside the typescript, but VSCode, git, and eslint ignore those omitted files.

Part of #601.
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
We will want these on later, but this cuts down on the typescript errors by 50%, getting us closer to a workable state, and later we can turn those on incrementally.

Part of #601.
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue May 30, 2022
jkomoros added a commit that referenced this issue Nov 18, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
We were switching to optional first which was confusing TimestampToFieldValue.

Part of #601.
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
Optional was happening before the fieldvalue check.

Part of #601.
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
This actually fixes a real bug I think.

Part of #601.
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
jkomoros added a commit that referenced this issue Nov 19, 2023
Last one?

Part of #601.
jkomoros added a commit that referenced this issue Nov 20, 2023
Card types without an icon type would have an alert icon.

Part of #601.
jkomoros added a commit that referenced this issue Nov 20, 2023
An error on the console.

Part of #601.
jkomoros added a commit that referenced this issue Nov 20, 2023
Which has always been true. This has a lot of downstream type implications, the vast majority of which
don't have particularly annoying semantics.

Part of #670. Part of #601.
jkomoros added a commit that referenced this issue Nov 21, 2023
Would show a warning icon for cards that didn't have an icon type configured.

Part of #601.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup No change in user behavior, just code cleanup and refactoring
Projects
None yet
Development

No branches or pull requests

1 participant