James Shubin ad0dd44130 engine: Don't force validation for hidden resources ...

I think this is what I want in most scenarios, is there a reason to do
otherwise? This is because we may wish to export incomplete resources,
where the remaining necessary fields for validation happens on collect.

2025-05-06 03:36:01 -04:00

..

ast

lang: ast: Refactor to unindent slightly

2025-04-27 22:19:14 -04:00

core

git: Update gitignore files

2025-05-06 02:52:26 -04:00

download

legal: Remove year

2025-01-26 16:24:51 -05:00

embedded

legal: Remove year

2025-01-26 16:24:51 -05:00

funcs

lang: funcs: structs: Pass through the type

2025-04-27 22:23:42 -04:00

fuzz

misc: Use /usr/bin/env for a more generic shebang

2025-03-22 14:53:21 -04:00

gapi

cli, gapi: Add more information that deploy is running

2025-03-12 05:45:26 -04:00

inputs

legal: Remove year

2025-01-26 16:24:51 -05:00

interfaces

lang: Improve graph shape with speculative execution

2025-04-27 22:14:51 -04:00

interpolate

git: Update gitignore files

2025-05-06 02:52:26 -04:00

interpret

engine: Fix up some send/recv corner cases

2025-05-05 23:53:37 -04:00

interpret_test

engine: Don't force validation for hidden resources

2025-05-06 03:36:01 -04:00

parser

git: Update gitignore files

2025-05-06 02:52:26 -04:00

types

lang: Improve graph shape with speculative execution

2025-04-27 22:14:51 -04:00

unification

lang: ast, gapi, interfaces, parser: Print line numbers on error

2025-02-25 20:15:02 -05:00

util

legal: Remove year

2025-01-26 16:24:51 -05:00

interpret_test.go

engine, lang: Modern exported resources

2025-04-05 12:45:23 -04:00

lang_test.go

legal: Remove year

2025-01-26 16:24:51 -05:00

lang.go

engine, lang: Modern exported resources

2025-04-05 12:45:23 -04:00

Makefile

misc: Use /usr/bin/env for a more generic shebang

2025-03-22 14:53:21 -04:00