freesewing/packages/core/tests/hooks.test.mjs

import chai from 'chai'
import { Pattern } from '../src/index.mjs'

const expect = chai.expect

describe('Hooks', () => {
  it('Should contain all hooks', () => {
    const pattern = new Pattern()
    const h = pattern.plugins.hooks
    const test = {
      preInit: [],
      postInit: [],
      preDraft: [],
      preSetDraft: [],
      prePartDraft: [],
      postPartDraft: [],
      postSetDraft: [],
      postDraft: [],
      preSample: [],
      postSample: [],
      preRender: [],
      preLayout: [],
      postLayout: [],
      postRender: [],
      insertText: [],
    }
    expect(h).to.eql(test)
  })
})
wip(core): Work on late-stage config resolver This moves resolving of the config from the pattern constructor to the init() method. The idea is that adding a part to a pattern is exactly the same as adding a part to a design. In other words, late-stage adding of parts would be no different as the config gets resolved after that. This is currently broken in many different ways, but the unit tests particular to this new way of resolving the config do pass. 2022-09-09 20:20:38 +02:00			`import chai from 'chai'`
			`import { Pattern } from '../src/index.mjs'`
chore(core): Port tests to ESM 2022-08-25 11:47:54 +02:00
			`const expect = chai.expect`
:white_check_mark: Tests for hooks 2018-08-12 12:37:30 +02:00
wip(core): Work on porting unit tests to v3 2022-08-27 09:27:07 +02:00			`describe('Hooks', () => {`
wip(core): Work on late-stage config resolver This moves resolving of the config from the pattern constructor to the init() method. The idea is that adding a part to a pattern is exactly the same as adding a part to a design. In other words, late-stage adding of parts would be no different as the config gets resolved after that. This is currently broken in many different ways, but the unit tests particular to this new way of resolving the config do pass. 2022-09-09 20:20:38 +02:00			`it('Should contain all hooks', () => {`
			`const pattern = new Pattern()`
refactor (core) reorganize method groupings in Pattern 2023-04-18 00:00:25 -04:00			`const h = pattern.plugins.hooks`
wip(core): Work on porting unit tests to v3 2022-08-27 09:27:07 +02:00			`const test = {`
feat(core): Added additional lifecycle hooks Specifically: - preInit - postInit - preSetDraft - prePartDraft - postPartDraft - postSetDraft 2022-09-18 22:48:55 +02:00			`preInit: [],`
			`postInit: [],`
wip(core): Work on porting unit tests to v3 2022-08-27 09:27:07 +02:00			`preDraft: [],`
feat(core): Added additional lifecycle hooks Specifically: - preInit - postInit - preSetDraft - prePartDraft - postPartDraft - postSetDraft 2022-09-18 22:48:55 +02:00			`preSetDraft: [],`
			`prePartDraft: [],`
			`postPartDraft: [],`
			`postSetDraft: [],`
wip(core): Work on porting unit tests to v3 2022-08-27 09:27:07 +02:00			`postDraft: [],`
			`preSample: [],`
			`postSample: [],`
			`preRender: [],`
get tests passing 2022-11-14 16:33:57 -06:00			`preLayout: [],`
feat(core): Added additional lifecycle hooks Specifically: - preInit - postInit - preSetDraft - prePartDraft - postPartDraft - postSetDraft 2022-09-18 22:48:55 +02:00			`postLayout: [],`
wip(core): Work on porting unit tests to v3 2022-08-27 09:27:07 +02:00			`postRender: [],`
			`insertText: [],`
wip(core): Work on late-stage config resolver This moves resolving of the config from the pattern constructor to the init() method. The idea is that adding a part to a pattern is exactly the same as adding a part to a design. In other words, late-stage adding of parts would be no different as the config gets resolved after that. This is currently broken in many different ways, but the unit tests particular to this new way of resolving the config do pass. 2022-09-09 20:20:38 +02:00			`}`
			`expect(h).to.eql(test)`
			`})`
			`})`