Skip to content

Releases: BellCubeDev/fomod-js

0.3.0 - Dependencies JSON + TSUp Bundling

20 Jun 04:01
ea808a6

Choose a tag to compare

Full Changelog: 0.2.7...0.3.0

0.2.7 - Re-Add The Build Step

28 Aug 23:57
010f05a

Choose a tag to compare

Pre-release

It appears that, while updating the publish workflow, I managed to remove the build step! Whoops! Added that back.

0.2.6 - Fix Step Children Not Being Added Properly

27 Aug 23:56
ba05166

Choose a tag to compare

This release addresses what are really two major bugs, though both small in terms of complexity. The now-resolved issues:

  • Step children would not be reordered every time they were serialized to elements; an invalid order would be kept. I've made a note to test element ordering before 1.0.0.
  • If the Step had <visible> child element, we'd try to set that child to its own parent! The silly bugs are the ones that get you.

Full Changelog: 0.2.5...0.2.6

0.2.5 - Fix Typo in Default Info.xsd URL

22 Apr 03:11
5f025e2

Choose a tag to compare

- export const DefaultInfoSchema = 'https://fomod.bellcube.dev/schemas/info.xsd';
+ export const DefaultInfoSchema = 'https://fomod.bellcube.dev/schemas/Info.xsd';

0.2.4 - Some Bug Fixes Related To Document Associations

20 Mar 02:38
28030b7

Choose a tag to compare

  • Fixed bug where a flag instance could be attached to a document twice, causing inconsistencies
  • Options now properly associate generated flag names with the document
  • DependenciesGroup will now forward associateWithDocument() down the tree
  • Preserve JSDoc comments in the final type definitions

0.2.3 - Option Flags! They're here! They're working!

09 Jan 23:28
2fe5df1

Choose a tag to compare

  • New abstract method on XmlRepresentation, associateWithDocument(), which applies any side-effects that an override of assignElement() might've handled in previous versions to both this element and its children. Called at the start of each asElement(), primarily so FlagInstancesByDocument is populated
  • New document config option, generateNewOptionFlagNames, which, when set to true, will discard existing option flag names for a document and generate new ones from scratch
  • Minor optimizations & recursion safeguards

0.2.2 - Move to LGPL 3.0 & Add to package.json

31 Dec 14:58
ec41d41

Choose a tag to compare

Move to LGPL-3.0 and Add License to package.json

0.2.1 - Rename Default Config Object & Update Readme

31 Dec 14:42
0fba881

Choose a tag to compare

DefaultFomodAsElementConfig ---> DefaultFomodDocumentConfig

0.2.0 - Document Config, Option Flags, Step Visibility Dependencies, & Bug Fixes

31 Dec 04:23
095b566

Choose a tag to compare

  • Added configuration options for parsing and serialization
  • Implemented the ability to specify a dependency on an option directly (without having to keep two or more flags in sync)
  • Added step visibility dependencies (a spec feature I'd just missed)
  • Reorganized project file structure for dependencies for code splitting purposes (options are probable next)
  • Fixed a number of bugs, including schema breakage, incorrect parsing, and other such issues

0.1.15 - More Exports

30 Dec 17:18
6541d4c

Choose a tag to compare

0.1.15 - More Exports Pre-release
Pre-release

Might help if we export the interfaces used in the flag and install instance maps.