You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In adding support for TypeScript to the codebase, we plan on enabling strict mode, which is a setting in tsconfig.json that the TypeScript team recommends which enables a bunch of other settings designed to promote higher code quality/design and catch more runtime errors.
The problem here is that if we enable strict mode, all of the packages we use that are written in TypeScript also have to have been developed with strict mode as well. This seems to be the case for the packages we use so far but for one: Keystone's ur-registry package. There is an issue open in the repo for this package to track enabling of strict mode, but this may involve fixing some issues in the codebase itself. We need to work with the Keystone team to do this in a way that doesn't break backward compatibility.
The text was updated successfully, but these errors were encountered:
In adding support for TypeScript to the codebase, we plan on enabling strict mode, which is a setting in
tsconfig.json
that the TypeScript team recommends which enables a bunch of other settings designed to promote higher code quality/design and catch more runtime errors.The problem here is that if we enable strict mode, all of the packages we use that are written in TypeScript also have to have been developed with strict mode as well. This seems to be the case for the packages we use so far but for one: Keystone's
ur-registry
package. There is an issue open in the repo for this package to track enabling of strict mode, but this may involve fixing some issues in the codebase itself. We need to work with the Keystone team to do this in a way that doesn't break backward compatibility.The text was updated successfully, but these errors were encountered: